Data can be replicated from one service to another, for most CygNet services. Some services, the Address Resolution Service (ARS) and Remote Service Manager (RSM), do not support replication. Additionally, some services, the Flow Measurement Service (FMS) and the Value History Service (VHS), handle replication slightly differently than is the case for other services.
See the following topics for more information about replication for the corresponding services.
Data will be replicated to a service of the same name on a different Domain ID. Since Domain IDs are specific to a host machine, this means the replicated and source services must run on separate machines.
Replication requires the setting of several keywords in the service configuration files of both the source and destination (replicated) services, as shown in the following examples.
|
|
|
|
| Configuration file for a source service on Domain 5412 | Configuration file for a replicated service on Domain 6412 |
The data in a replicated service is read-only. If you are using CygNet Explorer to view replicated data, the application will indicate that the data is from a replicated service. If you try to open a record, it will be read-only.
 |
| PNT Service replicating from another CygNet domain |
The files that store replication information are listed below.
| File | Description |
|---|---|
|
<ServiceName>.dat.edb |
The data file. This is built by the replicated service from the pulled data. |
|
<ServiceName>.inx.edb |
The index file. This is built by the replicated service from the pulled data. |
|
<ServiceName>.replnotify |
This file keeps track of the progress of replication so that the source and target keep in sync. The .replnotify is on the source service. |
|
<ServiceName>.replrcv |
This file keeps track of the progress of replication so that the source and target keep in sync. The .replrcv is on the target service. |
|
|
|
